翻訳と辞書 Words near each other ・ Transmigration (novel) ・ Transmigration program ・ Translation of axes ・ Translation of Han dynasty titles ・ Translation of neologisms into Chinese ・ Translation of the Eighteenth century Gothic novel ・ Translation of The Lord of the Rings into Swedish ・ Translation of the Relics of Saint Nicholas from Myra to Bari ・ Translation operator ・ Translation operator (quantum mechanics) ・ Translation plane ・ Translation project ・ Translation project (disambiguation) ・ Translation studies ・ Translation unit ・ Translation unit (programming) ・ Translation Wave ・ Translation-quality standards ・ Translational bioinformatics ・ Translational Centre for Regenerative Medicine ・ Translational drift ・ Translational efficiency ・ Translational frameshift ・ Translational Genomics Research Institute ・ Translational Health Science and Technology Institute ・ Translational lift ・ Translational medicine ・ Translational Neurodegeneration ・ Translational neuroscience ・ Translational partition function Dictionary Lists mini英和辞書 mini和英辞書 Webster 1913 Latin-English FOLDOC Wikipedia English ウィキペディア

翻訳と辞書　辞書検索 [ 開発暫定版 ] スポンサード リンク Translation unit (programming) ： ウィキペディア英語版 Translation unit (programming) In C programming language terminology, a translation unit is the ultimate input to a C compiler from which an object file is generated.〔(ISO/IEC 9899:TC3 - Committee Draft of the C99 Standard - Section 5.1.1.1 )〕 In casual usage it is sometimes referred to as a compilation unit. A translation unit roughly consists of a source file after it has been processed by the C preprocessor, meaning that header files listed in #include directives are literally included, sections of code within #ifdef may be included, and macros have been expanded. ==Context== A C program consists of ''units'' called ''source files'' (or ''preprocessing files''), which, in addition to source code, includes directives for the C preprocessor. A translation unit is the output of the C preprocessor – a source file after it has been preprocessed. Preprocessing notably consists of expanding a source file to recursively replace all #include directives with the literal file declared in the directive (usually header files, but possibly other source files); the result of this step is a ''preprocessing translation unit''. Further steps include macro expansion of #define directives, and conditional compilation of #ifdef directives, among others; this translates the preprocessing translation unit into a ''translation unit''. From a translation unit, the compiler generates an object file, which can be further processed and linked (possibly with other object files) to form an ''executable program''. Note that the preprocessor is in principle language agnostic, and is a lexical preprocessor, working at the lexical analysis level – it does not do parsing, and thus is unable to do any processing specific to C syntax. The input to the compiler is the translation unit, and thus it does not see any preprocessor directives, which have all been processed before compiling starts. While a given translation unit is fundamentally based on a file, the actual source code fed into the compiler may appear substantially different than the source file that the programmer views, particularly due to the recursive inclusion of headers. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Translation unit (programming)」の詳細全文を読む スポンサード リンク 翻訳と辞書 : 翻訳のためのインターネットリソース Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.